Autogenerated HTML docs for v1.7.11-3-g60475
diff --git a/gitglossary.html b/gitglossary.html index 764db46..47eb403 100644 --- a/gitglossary.html +++ b/gitglossary.html
@@ -841,7 +841,7 @@ branch’s <a href="#def_head_ref">head ref</a> from a remote <a href="#def_repository">repository</a>, to find out which objects are missing from the local <a href="#def_object_database">object database</a>, - and to get them, too. See also . + and to get them, too. See also <a href="git-fetch.html">git-fetch(1)</a>. </p> </dd> <dt class="hdlist1"> @@ -890,7 +890,7 @@ A <a href="#def_ref">named reference</a> to the <a href="#def_commit">commit</a> at the tip of a <a href="#def_branch">branch</a>. Heads are stored in a file in <tt>$GIT_DIR/refs/heads/</tt> directory, except when using packed refs. (See - .) + <a href="git-pack-refs.html">git-pack-refs(1)</a>.) </p> </dd> <dt class="hdlist1"> @@ -1168,7 +1168,7 @@ routines that help select changes that add or delete a given text string. With the <tt>--pickaxe-all</tt> option, it can be used to view the full <a href="#def_changeset">changeset</a> that introduced or removed, say, a - particular line of text. See . + particular line of text. See <a href="git-diff.html">git-diff(1)</a>. </p> </dd> <dt class="hdlist1"> @@ -1196,7 +1196,7 @@ <dd> <p> Pulling a <a href="#def_branch">branch</a> means to <a href="#def_fetch">fetch</a> it and - <a href="#def_merge">merge</a> it. See also . + <a href="#def_merge">merge</a> it. See also <a href="git-pull.html">git-pull(1)</a>. </p> </dd> <dt class="hdlist1"> @@ -1260,7 +1260,7 @@ A reflog shows the local "history" of a ref. In other words, it can tell you what the 3rd last revision in <em>this</em> repository was, and what was the current state in <em>this</em> repository, - yesterday 9:14pm. See for details. + yesterday 9:14pm. See <a href="git-reflog.html">git-reflog(1)</a> for details. </p> </dd> <dt class="hdlist1"> @@ -1278,7 +1278,7 @@ it as my origin branch head". And <tt>git push $URL refs/heads/master:refs/heads/to-upstream</tt> means "publish my master branch head as to-upstream branch at $URL". See also - . + <a href="git-push.html">git-push(1)</a>. </p> </dd> <dt class="hdlist1"> @@ -1362,8 +1362,8 @@ parents, even though they are recorded in the <a href="#def_commit_object">commit object</a>). This is sometimes useful when you are interested only in the recent history of a project even though the real history recorded in the upstream is much larger. A shallow repository - is created by giving the <tt>--depth</tt> option to , and - its history can be later deepened with . + is created by giving the <tt>--depth</tt> option to <a href="git-clone.html">git-clone(1)</a>, and + its history can be later deepened with <a href="git-fetch.html">git-fetch(1)</a>. </p> </dd> <dt class="hdlist1"> @@ -1375,7 +1375,7 @@ id itself, it is of the format <em>ref: refs/some/thing</em> and when referenced, it recursively dereferences to this reference. <em><a href="#def_HEAD">HEAD</a></em> is a prime example of a symref. Symbolic - references are manipulated with the + references are manipulated with the <a href="git-symbolic-ref.html">git-symbolic-ref(1)</a> command. </p> </dd> @@ -1487,15 +1487,15 @@ </div> <h2 id="_see_also">SEE ALSO</h2> <div class="sectionbody"> -<div class="paragraph"><p>, -, -, +<div class="paragraph"><p><a href="gittutorial.html">gittutorial(7)</a>, +<a href="gittutorial-2.html">gittutorial-2(7)</a>, +<a href="gitcvs-migration.html">gitcvs-migration(7)</a>, <a href="everyday.html">Everyday git</a>, <a href="user-manual.html">The Git User’s Manual</a></p></div> </div> <h2 id="_git">GIT</h2> <div class="sectionbody"> -<div class="paragraph"><p>Part of the suite.</p></div> +<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite.</p></div> </div> </div> <div id="footnotes"><hr /></div>
